Use of touch and gestures related to tasks and business workflow

ABSTRACT

A business data system generates a user interface display showing a business data record. The business data system receives a touch gesture user input to manipulate the business data record to perform an operation, a task or a workflow within the business data system. The business data system performs the operation, task or workflow based on the touch gesture user input.

BACKGROUND

There are a wide variety of different types of business data systems.Some such systems include customer relations management (CRM) systems,enterprise resource planning (ERP) systems, line-of-business (LOB)applications, and other business systems. These types of systems oftenenable creation and maintaining of business data records. Some of theserecords include customer records that have details about customers,vendor records that include details of vendors, sales records, salesproposals, quotes, order records, records that contain product orservice information, and records related to business contacts, amongmany others. The system can also include workflows that enable users toperform various tasks and workflows using the business data system.

An example of a workflow provided in some business data systems is onethat allow(s) users or organizations to track various businessopportunities. For instance, if there is an opportunity to make a saleof products or services to another organization, the business datasystem allows users to enter information that may be helpful inconverting that opportunity into an actual sale. Similarly, some suchsystems allow many other types of tasks or workflows to be performed aswell. For instance, some systems allow users to prepare a quote for apotential customer. Then, when the customer accepts the terms of thequote, the user can convert the quote into an actual order. These aremerely two examples of a wide variety of different types of tasks andworkflows that can be performed within a business data system.

In performing these and other types of tasks and workflows, some usersmay wish to contact other people associated with the business datarecords being operated on. For instance, where a customer has a primarycontact, it may be that the user wishes to call or otherwise communicatewith that person in order to discuss the terms of a proposal or order.Therefore, some business data systems allow a user to search forcontacts, and communicate with a given contact.

The use of mobile devices is also increasing rapidly. Some mobiledevices include smart phones, cellular telephones, and tablet computers,to name a few. These types of devices often have different types of userinput mechanisms than desktop computers. For example, a desktop computermay have user interface displays with user input mechanisms that can beactuated by a point and click device (such a mouse or track ball) or ahardware keyboard. However, mobile devices often have touch sensitivescreens. This enables a user to actuate user input mechanisms usingtouch gestures, such as by using a finger, a stylus, or other device.

The discussion above is merely provided for general backgroundinformation and is not intended to be used as an aid in determining thescope of the claimed subject matter.

SUMMARY

A business data system generates a user interface display showing abusiness data record. The business data system receives a touch gestureuser input to manipulate the business data record to perform anoperation, a task or a workflow within the business data system. Thebusiness data system performs the operation, task or workflow based onthe touch gesture user input.

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used as an aid in determining the scope of the claimed subjectmatter. The claimed subject matter is not limited to implementationsthat solve any or all disadvantages noted in the background.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of one illustrative business data environment.

FIG. 2A is a flow diagram of one embodiment of the operation of thesystem shown in FIG. 1 in performing a task based on a touch gesture.

FIG. 2B is a flow diagram of one embodiment of the operation of thesystem shown in FIG. 1 in manipulating contact information based on atouch gesture.

FIG. 2C is a flow diagram illustrating one embodiment of the operationof the system shown in FIG. 1 in manipulating a contact, within abusiness record, using touch gestures.

FIGS. 3A-3F show exemplary user interface displays.

FIG. 4 is a flow diagram illustrating one embodiment of the operation ofthe system shown in FIG. 1 in receiving touch gestures to generatesuggestions of information to add to a business record based on partialinformation.

FIG. 5 is a flow diagram illustrating one embodiment of the operation ofthe system shown in FIG. 1 in adding product information to a businessopportunity based on touch gestures.

FIGS. 5A-5C are illustrative user interface displays.

FIG. 6 is a flow diagram illustrating one embodiment of the operation ofthe system shown in FIG. 1 in receiving touch gestures to add decisionmakers to a business record, based on touch gestures.

FIGS. 6A-6I show illustrative user interface displays.

FIG. 7 is a flow diagram illustrating one embodiment of the operation ofthe system shown in FIG. 1 in adding team members to a business record,based on touch gestures.

FIGS. 7A-7I show illustrative user interface displays.

FIG. 8 is a flow diagram illustrating one embodiment of the operation ofthe system shown in FIG. 1 in manipulating a document corresponding to abusiness record based on touch gestures.

FIGS. 8A-8O show exemplary user interface displays.

FIG. 9 shows one embodiment of the system shown in FIG. 1 in differentarchitectures.

FIGS. 10-14 illustrate various mobile devices.

FIG. 15 is a block diagram of one illustrative computing environment.

DETAILED DESCRIPTION

FIG. 1 shows one illustrative embodiment of a business data architecture90. Business data architecture 90 includes CRM system 100, CRM datastore 102 and user device 104. User device 104 is shown generating userinterface displays 106 for interaction by user 108. FIG. 1 also showsthat CRM system 100 can be connected to, or connectable to access, otherexternal systems 109. While CRM system 100 can be any business datasystem (such as a CRM system, an ERP system, an LOB system, or anotherbusiness data application or business data system) it is describedherein as a CRM system, for the sake of example only.

CRM system 100 illustratively includes processor 110, search component111, user interface component 112, connection generator 113,communication component 114, suggestion component 115, team selectorcomponent 116, decision maker selection component 117, workflow/taskcomponent 118, document management component 119, follow-up component120 and other CRM components 121.

Processor 110 is illustratively a computer processor with associatedmemory and timing circuitry (not separately shown). It is a functionalpart of CRM system 100 and is activated by, and facilitates thefunctionality of, the other components and items in CRM system 100. Itwill also be noted that while only a single processor 110 is shown,processor 110 can actually be multiple different computer processors aswell. In addition, the multiple different computer processors used bysystem 100 can be local to system 100, or remote from system 100, butaccessible by system 100.

Search component 111 illustratively generates user interface displayswith user input mechanisms that can be actuated by user 108. Theinterface displays allow user 108 to use touch gestures to search forinformation in data store 102 or external system 109, or both, usingtouch gestures.

User interface component 112 illustratively generates user interfacedisplays with user input mechanisms that can be actuated by user 108using touch gestures. The user interface displays 106 (that user 108interacts with) can be generated by user interface component 112 in CRMsystem 100 and passed to device 104 where they can be displayed (bydevice 104, as user interface displays 106) for interaction by user 108.

Connection component (or connection generator) 113 illustratively allowsuser 108 to find connections between various people using touchgestures. Connection component 113, in one embodiment, can use variousmetrics to calculate a strength of connection as well. This is describedin greater detail below with respect to FIGS. 6C-6E.

Communication component 114 illustratively facilitates communicationamong various users of CRM system 100, or between users of CRM system100 and other individuals who may not necessarily be users of system100, based on touch gestures. For instance, if user 108 wishes tocommunicate with a contact who may not necessarily have access to CRMsystem 100 (such as by initiating a phone call, an instant message,etc.), communication component 114 illustratively facilitates this typeof communication. Therefore, communication component 114 canillustratively facilitate email communication, telephone or cellulartelephone communication, instant message communication, chat roomcommunication, or other types of communication.

Suggestion component 115 illustratively receives user inputs (throughtouch gestures) and makes suggestions to the user based on those inputs.For instance, where a user is generating a sales proposal or anopportunity for a given company, suggestion component 115 can use searchcomponent 111 to search for information on the given company andgenerate a suggestion for additional products or services that the usermay wish to include in the opportunity or proposal. Similarly, where theuser is attempting to identify an individual to fill a position as ateam member, for instance, suggestion component 115 can access variouspersonnel information in data store 102 and make suggestions forindividuals to fill that position on the team. In making suggestions,suggestion component 115 can use a wide variety of different types ofinformation. Some of these are described below in greater detail withrespect to FIGS. 5A-5C.

Team selector component 116 illustratively generates user interfacedisplays with user input mechanisms that allow user 108 to use touchgestures to configure a team, and select team members corresponding to abusiness record. For instance, where user 108 identifies a businessopportunity, user 108 can generate a business record representing thatopportunity. In doing so, user 108 may wish to assemble a team (or atleast request a team) to work on pursuing that business opportunity.Team selector component 116 illustratively walks the user through theprocess of identifying team members and selecting them for the team. Oneembodiment of this is described in greater detail below with respect toFIGS. 7A-7I.

Decision maker selection component 117 illustratively generates userinterface displays that allow user 108 to use touch gestures to identifydecision makers corresponding to a business record. Again, taking theexample that the business record represents a business opportunity, user108 may attempt to identify the people at the business opportunity thatare the decision makers that are to be persuaded in order to make asale. One embodiment of this is described in greater detail below withrespect to FIGS. 6-6G.

Workflow/task component 118 illustratively generates user interfacedisplays 106 so that user 108 can perform other tasks and carryout otherworkflow within CRM system 100 using touch gestures. For instance,workflow/task component 118 illustratively allows user 108 to addcontact information to CRM system 100, to track opportunities withinsystem 100, to convert quotes to orders, or to input various other typesof information or perform other tasks or workflows, using touchgestures.

Document management component 119 illustratively generates userinterface displays 106 that allow user 108 to perform various documentmanagement tasks using touch gestures. A number of different embodimentsof this are discussed below with respect to FIGS. 8-8F.

Follow-up component 120 illustratively uses user interface component 112to generates user interface displays that allow user 108 to generate afollow-up directly from a business data record within CRM system 100,using touch gestures. One illustrative embodiment of this is describedbelow with respect to FIGS. 8F-8N.

Other CRM components 121 illustratively provide the functionality forother things that can be done in CRM system 100. There are a widevariety of other things that users can do within CRM system 100, andthese various functions are provided by other components 121.

It will be noted that in one embodiment, the various items that generateuser interface displays can do so using component 112. In anotherembodiment, some or all of the items generate the user interfacedisplays themselves, without using component 112. Both are contemplatedherein.

CRM system 100 has access to CRM data store 102. CRM data store 102illustratively stores a variety of different business data records.While data store 102 is shown as a single data store, it can be multipledifferent data stores. It can be local to system 100 or remotetherefrom. Where it includes multiple different data stores, they canall be local to or remote from system 100, or some can be local whileothers are remote.

The data records can include, by way of example only, proposals 124,opportunities 126, quotes 128, customer data records 130, orders 132,product/service information 134, vendor records 136, contacts 138,connection graphs 139, workflows 140, personnel information 141, andother business data records 142. Each of the business data records maybe an object or entity, or another type of record. The records caninclude links to other records, or stand by themselves. All of thesetypes of structures, and others are contemplated herein.

Proposals 124 illustratively include business information for a proposalthat can be made to a customer. Opportunities 126 illustratively includea wide variety of different types of information (some of which isdescribed below with respect to FIGS. 3A-3F) that enable user 108 totrack a sales opportunity within CRM system 100. Quotes 128illustratively include information defining quotes that can be providedto customers. Customers 130 include customer information, such ascontact information, address, billing information, etc. for differentcustomers. Orders 132 illustratively include order information thatreflects orders that have actually been made by various customers.Product/service information 134 illustratively includes information thatdescribes products or services in CRM system 100. Vendors 136illustratively include information describing vendors that are used bythe organization in which CRM system 100 is deployed. Contacts 138illustratively include contact information for various people that areeither users of CRM system 100, or that are related to any of the otherbusiness data records in CRM data store 102 (for instance they can becontacts at vendors, customers, other users, etc.).

Connection graphs 139 illustratively show how various people in CRMsystem 100, or outside system 100, are connected to one another. Forinstance, if person A is the boss of person B and person B is on thesame team for a project as person C, then the connection graph betweenperson A and person C might be:

person A→person B→person C,

meaning that person A and person C are connected through person B. Ofcourse, the connection graphs can have substantially any length and awide variety of different connection criteria. Also, they can takedifferent forms, the connections can be labeled, etc.

Workflows 140 illustratively define the various workflows that user 108can perform within CRM system 100. The workflows can take a wide varietyof different forms. For instance, they may simply be data entryworkflows, workflows posting information to a ledger, workflows fleshingout proposals or quotes, or a wide variety of other things. In any case,CRM system 100 accesses workflows 140 in order to generate the userinterface displays 106 that can be manipulated by user 108, in order toperform the different workflows.

User device 104 illustratively includes user interface component 122,client CRM system 144, and processor 146. Client CRM system 144 isillustratively used by user device 104 in order to access CRM system100. Of course, client CRM system 144 can be a stand alone system aswell, in which case it has access to CRM data store 102, or a differentCRM data store. As described herein, however, it is simply used in orderto access CRM system 100. This is but one option.

User interface component 122 illustratively generates the user interfacedisplays 106 on user device 104. In the embodiment described herein,device 104 has a touch sensitive user interface display screen.Therefore, user interface component 122 illustratively generates thedisplays for display on the user interface display screen. The displays106 have user input mechanisms 107 that can be actuated, using touchgestures, by user 108.

Processor 146 is illustratively a computer processor with associatedmemory and timing circuitry (not separately shown). Processor 146 isillustratively a functional part of device 104 and is activated by, andfacilitates the functionality of, the other systems, components anditems in device 104. While processor 146 is shown as a single processor,it could be multiple processors as well.

As briefly discussed above, user interface displays 106 areillustratively user interface displays that are provided for interactionby user 108. User input mechanisms 107 can be a wide variety ofdifferent types of user input mechanisms. For instance, they can bebuttons, icons, text boxes, dropdown menus, soft keyboards or virtualkeyboards or keypads, links, check boxes, active tiles that function asa link to underlying information or applications or functions and thatactively or dynamically show information about the underlyinginformation, application or function, or a wide variety of other userinput mechanisms that can be actuated using touch gestures.

It will also be noted that the touch gestures mentioned herein can takea wide variety of different forms. They can be simple touches or taps,swipes, slides, multi-touch inputs, positional gestures (gestures at aspecific position or location on the screen), brushing, multi-fingergestures, touch and hold gestures, etc. The speed of the gestures can beused for control as well (e.g., a quick swipe can pan quickly while aslow swipe pans slowly, etc.). These and other gestures are allcontemplated herein.

FIG. 2A is a flow diagram illustrating one embodiment of the operationof the architecture shown in FIG. 1 in performing a task or workflow orother operation based upon a touch gesture received from a user.Depending on the particular task workflow or operation to be performed,one of the components in CRM system 100 illustratively uses userinterface component 112 to generate a user interface display with a userinput mechanism that allows user 108 to perform the task, workflow, oroperation, in CRM system 100. This is indicated by block 143 in FIG. 2A.

CRM system 100 then receives a touch gesture on the user input mechanismindicating that the user wishes to perform the task, workflow oroperation. This is indicated by block 145.

In response to the touch gesture, CRM system 100 (or a specificcomponent or set of components or items in CRM system 100) perform thetask within the CRM system 100 based upon the touch gesture. This isindicated by block 147 in FIG. 2A.

Of course, the task, workflow or operation can be one of a wide varietyof different ones, and some of those are shown in FIG. 2A. For instance,search component 111 can search an internal or external system (such asCRM data store 102, or a data store associated with one of externalsystems 109). This is indicated by block 99 in FIG. 2A. One or more ofthe components or items in CRM system 100 can also create a link in theCRM system to internal or external data records. This is indicated byblock 101. Similarly, the CRM system 100 can attach internal or externalinformation directly to an open business record, as indicated by block103. CRM system 100 can manipulate contact information based on thetouch gesture as indicated by block 105. Suggestion component 115 canaccess a variety of different types of information and make suggestionsto user 108 based on the touch gesture. This is indicated by block 149.Decision maker selection component 117 can identify decision makers, asindicated by block 151. Document management component 119 can performdocument management steps based on the touch gestures as indicated byblock 153, and follow component 120 can generate follow-ups within CRMsystem 100, based on the touch gesture. This is indicated by block 155.Team selector component 116 can configure a team or add a team member,as indicated by block 157. Of course, CRM system 100 can perform a widevariety of other tasks, workflows or operations based on the touchgesture and this is indicated by block 159.

FIG. 2B is a flow diagram illustrating one embodiment of the operationof the architecture shown in FIG. 1 in manipulating contacts using touchgestures within CRM system 100. User 108 first illustratively providesan input indicating that he or she wishes to access CRM system 100. Thiscan launch client CRM system 144 which provides access to CRM system100, or it can launch CRM system 100 and provide direct or indirectaccess. In response, CRM system 100 uses user interface component 112 togenerate a user interface display 106 that displays a wall or other CRMdisplay. Launching the CRM system is indicated by block 167 in FIG. 2B,and displaying the wall (or start screen) display is indicated by block169. The CRM display illustratively includes user input mechanisms 107that allow user 108 to manipulate them and thus control and manipulateCRM system 100.

FIG. 3A is one illustrative example of a user interface display 200 thatshows a wall or a CRM start screen. Display 200 is shown on user device202 which is illustratively a tablet computer. Tablet computer 202illustratively includes touch sensitive display screen 204. Of course,it will be noted that device 202 could be any other type of device thathas a touch sensitive display screen. Start screen (or wall) 200 isshown with a plurality of tiles, or icons 206.

In the embodiment shown in FIG. 3A, the icons (or tiles) are dividedgenerally into two different sections. The first section is a personalsection 208, and the second section is a business section 210. Thesesections are exemplary only and may or may not be used. The tiles insection 208 are illustratively user actuatable links which, whenactuated by a user, cause a corresponding function to happen. Forexample, when either one of a pair of browser tiles 210 or 212 areactuated by the user, they launch a browser. When store tile 214 isactuated by the user, it launches an on-line store application orportal. Other tiles are shown for navigating to the control panel, forviewing weather, for viewing stock information of identified companies,or that indicate popular browsing sessions. Of course, the tiles shownin the personal section 208 are exemplary only and a wide variety ofadditional or different tiles could be shown as well.

The business section 210 of start display 200 also includes a pluralityof tiles which, when actuated by the user, cause the CRM system 100 totake action. For instance, contact tile 216, when actuated by the user,opens a contact menu for the user. Opportunities tile 218, when actuatedby the user, opens opportunity records or an opportunities menu thatallows the user to navigate to individual opportunity records. The “myleads” tile 220, when actuated by the user, causes the CRM system 100 toopen a menu or records corresponding to leads for the given user. A newstile 222 provides news about one or more items that have taken place inCRM system 100, and that are of interest to the user.

In the example shown in FIG. 3A, tile 222 shows that an opportunity forthe ACME Company has been closed by another sales person. When the useractuates tile 222, the CRM system 100 navigates the user to additionalinformation about that closed opportunity. For instance, it may navigatethe user to the opportunity record or to the sales record, or simply tothe ACME Company general record. The other tiles, when actuated by theuser, cause the CRM system to navigate the user to other places ofinterest or to launch other components of the CRM system. Thosedisplayed are shown for the sake of example only.

Once the CRM system 100 is launched and the start screen is displayed,CRM system 100 then receives a user touch gesture to manipulate acontact in CRM system 100. This is indicated by block 171 in FIG. 2B. Byway of example, the user can simply touch contacts tile 216. This causesCRM system 100 to display a contact menu that allows the user to take avariety of other actions, such as to open a contact 173, edit a contact175, add or delete contacts 177, initiate communication with one or morecontacts 179, schedule a meeting with a contact 181, touch a searchbutton to begin a search 183 for a contact, or perform other contactmanipulation steps 185. In response, CRM system 100 manipulates thecontact based on the touch gestures. This is indicated by block 187 inFIG. 2B.

It should also be noted that the user can manipulate contacts in otherways as well. For instance, instead of actuating contact tile 216, orone of the specific contacts represented by the photos or images on tile216, the user may open up other business data records in CRM system 100.Many of those business data records may have individual people, orcontacts, associated with them. Therefore, user 108 can manipulatecontacts from within those business data records as well.

FIG. 2C is a flow diagram illustrating one embodiment of this type ofcontact manipulation. The first two blocks in FIG. 2C are similar to thefirst two blocks shown in FIG. 2B, and they are similarly numbered.Therefore, at block 167, the user launches the CRM system 100 and atblock 169 the CRM system 100 displays a start display or wall or otherCRM user interface display.

In the embodiment shown in FIG. 2C, the user then provides a touchgesture to open a CRM record. FIG. 3B shows one example of this. In theembodiment shown in FIG. 3B, the user has illustratively actuated tile218, such as by touching it. In response, CRM system 100 displays anopportunities tile 224. Opportunities tile 224 is illustrativelyindicative of a new opportunity that has been created. The user thenactuates tile 224, using a touch gesture (e.g., by touching it) with hisor her finger 226. This causes CRM system 100 to open another userinterface display, such as user interface display 228 shown in FIG. 3C,corresponding to the newly created opportunity. Receiving the user inputto open the CRM record is indicated by block 320 in FIG. 2B, and havingthe CRM system 100 display the record is indicated by block 322.

FIG. 3C shows that the business record display 228 displays tiles orlinks (or other icons or user-actuatable items) that allow the user toview a variety of different kinds of information. For instance, display228 includes a “people” or “contact” tile 230. Tile 230 identifiespeople either at the organization for which the opportunity has beengenerated, or at the organization that employs the CRM system, that aresomehow related to the opportunity. By way of example, the opportunitytile 230 may link user 108 to other people in the company that employsthe CRM system, who are working on converting the opportunity into anactual sale. In addition, tile 230, when actuated by the user, maynavigate the user to contact information for individuals at the companyfor which the opportunity was developed. In any case, if the useractuates tile 230, the CRM system 100 illustratively navigates user 108to either a contact menu or a specific contact and allows the user tomanipulate the contact in a similar way as described above with respectto FIG. 2B. For instance, the user can open a contact, delete or editit, initiate communication, etc.

FIG. 3C also shows examples of other information that can be shown in abusiness data record. For instance, user interface display 228 includesa wide variety of actuable items that take the user to other informationcorresponding to the opportunity. Invoices tile 232, when actuated bythe user, navigates the user to another display where the user can viewinformation related to invoices that correspond to this opportunity.Quotes tile 234, when actuated by the user, navigates the user toadditional information about quotes generated for this company orsomehow related to this opportunity. Document tile 236 illustrativelynavigates the user to other related documents corresponding to thisopportunity, and activity tile 238 shows, in general, the amount ofactivity related to this opportunity. When the user actuates tile 238,CRM system 100 can navigate the user to additional displays showing thespecific activity represented by the tile 238.

User interface display 228 also illustratively includes a “What's new”section 240. What's new section 240 can display posts by user 108, orother users of the CRM system, that are related to the opportunity beingdisplayed.

In addition, as shown in FIG. 3C, display 228 is illustratively pannablein the directions indicated by arrow 242. By way of example, if the useruses his or her finger 226 and makes a swiping motion to the left or tothe right, display 228 illustratively pans to the left or to the rightbased on the touch gesture.

User interface display 228 also illustratively includes an informationsection 244 that displays a primary contact tile 246 corresponding to aprimary contact for this opportunity. A plurality of additional tiles248 are displayed below the primary contact tile 246, and provideinformation corresponding to the individual represented by primarycontact tile 246. The tiles 248, for instance, provide a preferredcontact method for the primary contact, an amount of revenue generatedby the primary contact, an indicator of the availability of the primarycontact, a reputation or rating for the primary contact, a date when theopportunity corresponding to the primary contact closes, and a creditlimit for the primary contact. Of course, all of the tiles 248 areexemplary only, and additional or different information corresponding tothe primary contact, or other information, can be displayed as well.

Since the opportunity record represented by user interface 228 has aprimary contact (or tile) 246 that represents the primary contact forthe displayed opportunity, the user can manipulate that contactinformation from within the opportunity business record displayed inuser interface display 228. If there were no contact informationcorresponding to the business opportunity displayed on display 220, CRMsystem 100 would illustratively provide a user input mechanism thatallows user 108 to navigate to contact information corresponding to thedisplayed business data record. Determining whether contact informationis displayed on the business data record represented by user interfacedisplay 228 is indicated by block 324 in FIG. 2C. If not, receiving theuser touch gesture to show contact information is indicated by block326.

As described above, in the embodiment shown in FIG. 3C, both the contacttile 230 and the primary contact tile 246 are shown in user interfacedisplay 228. Therefore, the user need not provide an additional touchgesture to see contact information.

FIG. 3C also shows that the user is using his or her finger 226 toactuate tile 246. Thus, user 108 is selecting primary contact 246, byactuating the corresponding tile. Receiving a touch gesture selecting acontact is indicated by block 328 in FIG. 2C.

Actuation of tile 146 causes CRM system 100 to generate another userinterface display that allows the user to manipulate the contactinformation. As described above with respect to FIG. 2B, this can take awide variety of different forms. However, in the embodiment discussedwith respect to FIG. 2C, actuating primary contact tile 246 causes CRMsystem 100 to generate a display, such as user interface display 250,shown in FIG. 3D. It can be seen that a number of the items in userinterface display 250 are the same as those shown in user interfacedisplay 228 in FIG. 3C, and they are similarly numbered. However, FIG.3D also shows that, since the user actuated tile 246, this causes CRMsystem 100 to display communication bar 252. Communication bar 252displays the specific contact options for the selected contact, who wasselected when the user actuated tile 246. Communication bar 252, itself,illustratively includes a plurality of user actuatable items each ofwhich represents a method for contacting the primary contact representedby tile 246. For instance, communication bar 252 includes phone button332, email button 334, instant messenger button 336 and other button338. Displaying the specific contact options for the selected contact isindicated by block 330 in FIG. 2C.

When the user actuates any of the buttons in communication bar 252, thiscauses CRM system 100 to illustratively initiate communication with theprimary contact using the selected method of communication. FIG. 3Dshows that the user 108 has used his or her finger 226 to actuate thephone button 332. In the embodiment shown, the user simply touchesbutton 332 to actuate it. Receiving the user touch gesture selecting acontact option is indicated by block 340 in FIG. 2C and performing thecommunication using the selected option is indicated by bock 342.

In response to the user actuating the phone button 332, communicationcomponent 114 in CRM system 100 illustratively initiates a phone call tothe primary contact “Phil B.” represented by tile 246 and generates asuitable user interface display indicating that the call has beeninitiated. FIG. 3E shows one exemplary user interface display 300 thatillustrates this. It can be seen in display 300 that a phone call isunderway to Phil B. This is indicated generally at 302. Display 300shows the identity of the person being called, an indication that it isa phone call, and the elapsed time of the call. Of course, thisinformation is exemplary only and a wide variety of additional ordifferent information can be shown as well. In any case, user interfacedisplay 300 illustrates that a call has been placed.

A number of other exemplary things are shown in display 300. A list ofobjectives to be accomplished are shown generally at 306. A status bar304 shows how many of the objectives for the phone call have beencompleted. The objectives listed are “product requirements”, “keydecision makers”, “budget”, and “notes”. In one embodiment, these arethe agenda items for the phone call. Of course, they may be simply “todo” items or a variety of other listed items as well.

FIG. 3E also shows that a soft keyboard is displayed generally at 308.This allows user 108 to type information into the text boxes at 306, orto otherwise enter alphanumeric information, using touch.

The communication (e.g., the telephone call) can proceed until one ofthe parties stops the communication. This can be done, in oneembodiment, by user 108 simply touching an appropriate button on theuser interface display. FIG. 3F shows one illustrative way of doingthis. FIG. 3F shows user interface display 310, which is similar to userinterface display 300 shown in FIG. 3E, and similar items are similarlynumbered. However, it can be seen in FIG. 3F that the parties to thecall have accomplished two of the agenda items, and therefore status bar304 shows that two out of four items have been completed. Display 310also shows that the user has touched a “hang up” button 312. Hang upbutton 312 allows user 108 to terminate the call, simply by actuatingbutton 312. Receiving a user touch gesture to end the communication isindicated by block 344 in FIG. 2C. In response, communication component114 of CRM system 100 hangs up the call, or disconnects the call, orotherwise discontinues the telephone communication. This is indicated byblock 346 in FIG. 2C.

It can thus be seen that a user can quickly and easily manipulatecontact information within a CRM system, or other business data system.When contact information is displayed, the user can use a touch gestureto manipulate it. This can make manipulation of contact information mucheasier and less cumbersome.

FIG. 4 is a flow diagram illustrating one embodiment of the operation ofthe system shown in FIG. 1 in receiving partial information from a userbased on touch gestures, performing a search, and suggesting additionalinformation. It will be noted that, the system can perform the operationshown in FIG. 4 in order to perform a wide variety of tasks, workflows,or operations. For instance, when user 108 is searching for productinformation, user 108 can provide partial product information in asearch box and system 100 can perform its own searching and suggestadditional information. Similarly, when user 108 is looking for anindividual person, user 108 can provide partial information and system100 can perform searching and suggest additional information. While theoperation discussed with respect to FIG. 4 is general in nature, anumber of specific examples are discussed in greater detail below, forthe sake of enhanced understanding.

First, in order to provide additional information, based on partialinformation, user interface component 112 (under the direction ofanother component or item in CRM system 100) displays a user interfacedisplay to add information to a business record. This is indicated byblock 350 in FIG. 4. The user interface display illustratively has userinput mechanisms that allow user 108 to provide partial information thatcan be used by system 100 in suggesting additional information.

System 100 then receives a touch input from the user, that provides thepartial information. This is indicated by block 352. By way of example,if the user 108 is looking for a specific individual, the user may onlyknow that individual's first name and the first letter of their lastname. Therefore, the user can provide this using touch, through avirtual keyboard (for instance), and search component 111 can searchpersonnel information in CRM data store 102 or in external systems 109.Based on the returned search results, suggestion component 115 cansuggest a full personnel record based on the partial information (thefirst name and last letter of the last name) input by the user. This isbut one example.

In another example, if user 108 is attempting to identify products thatmight be sold to an organization that has been identified as a businessopportunity, search component 111 can search the available informationon an external system 109 corresponding to the organization. Searchcomponent 111 can return product information indicative of products thatare sold or used by the organization. Based on this information,suggestion component 115 can suggest additional products or servicesthat may be sold to the organization. This additional information can beadded to the opportunity data record corresponding to that organization.This is exemplary only.

Continuing with the more general discussion of FIG. 4, once user 108provides the partial information using touch inputs, search component111 searches for the additional information. This is indicated by block354 in FIG. 4. As briefly mentioned above, search component 111 cansearch CRM data store 102 (or any other data store that is part ofsystem 100) or it can search external systems 109. The external systemscan be accessed over a wide area network (such as the Internet) or theycan be any other desired external systems as well. Searching internalsystems is indicated by block 356 in FIG. 4 and searching externalsystems is indicated by block 358.

Based upon the returned search results, suggestion component 115generates and displays suggestions of information to add to the businessrecord. This is indicated by block 360 in FIG. 4.

System 100 then receives a touch gesture selecting information to beadded to the business record. This is indicated by block 362 in FIG. 4.By way of example, suggestion component 115 may suggest a list of names,or a list of additional products or services that may be sold to thecompany corresponding to the business opportunity. The user can touchany of these items to have them added. Based upon the user's touchgesture, system 100 adds the selected information to the businessrecord. This is indicated by block 364 in FIG. 4. Again, by way ofexample, system 100 can add a name as a contact to the businessopportunity record or can add the additional product information to thebusiness opportunity record, etc. Both of these examples are describedbelow in greater detail.

System 100 can add the information to the business record in a varietyof different ways. For instance, system 100 can simply copy theinformation to the business record, as indicated by block 366. However,where the information resides on an external system (or even where itresides on an internal data store), system 100 can create a link in thebusiness record to the selected information. This is indicated by block368. Of course, system 100 can add the selected information to thebusiness record in other ways as well, and this is indicated by block370.

FIG. 5 is a flow diagram illustrating one embodiment of the operation ofthe system shown in FIG. 1 in adding specific information to a businessrecord. FIGS. 5A-5B are illustrative user interface displays. FIGS. 5-5Bwill now be discussed in conjunction with one another.

In the embodiment discussed with respect to FIG. 5, the user wishes toadd product information to an opportunity business record. The productinformation is information that identifies products that user 108 may beable to sell to the company represented by the business opportunityrecord. This is but one example of information that can be added to abusiness data record, using touch gestures.

In order to perform this operation, one of the components (such asworkflow/task component 118 or other CRM component 121) in CRM system100 uses user interface component 112 to generate a user interfacedisplay that can be used by user 108 to add product information to anopportunity business record. This is indicated by block 372 in FIG. 5.

CRM system 100 then receives a touch input from user 108 that providespartial product information to be added to the business opportunityrecord. This is indicated by block 374. FIG. 5A shows one example of auser interface display 376 that is similar to user interface display300, shown in FIG. 3E, except that the user has used virtual keyboard308 to enter “performance tires” in text box 378. This indicates theproducts that user 108 wishes to sell to the company (ACME)corresponding to the business opportunity record displayed.

Search component 111 then receives the partial information (“performancetires”) and searches, in this embodiment, the external system 109corresponding to the ACME Company in an attempt to identify any otherproducts or services that user 108 may be able to sell to that company.Of course, search component 111 can also search internal records if theyare helpful. For example, it may be that the company that user 108 worksfor has already sold some products or services to the ACME Company, inother parts of the country. That information may be helpful inidentifying additional products or services as well. In any case,searching for additional product information is indicated by block 480in FIG. 5.

The information from search component 111 is then returned to suggestioncomponent 115. Suggestion component 115 generates and displayssuggestions for additional product information that can be added to thebusiness opportunity record shown in FIG. 5A. This is indicated by block382 in FIG. 5. FIG. 5A shows that suggestion component 115 (e.g., usinguser interface component 112) has displayed a set of suggested products384, along with a success indicator. For instance, the first entry inthe suggested products 384 states “80% Company A cross trainers”. Thesecond entry states “60% extended 2 year service plan”, and the thirdentry states “40% helmets”.

Each of these entries are illustratively user actuatable buttons orlinks. When actuated, they cause CRM system 100 to display additionalinformation corresponding to the actuated link. FIG. 5B is an example ofa user interface display 386 which is similar to user interface display376 shown in FIG. 5A, except that it shows that the user has touched thefirst entry in suggested products 384. This causes system 100 toretrieve and display more detailed information about the selectedbutton, and this is shown generally at 388. Receiving the touch gestureto display more detail is indicated by block 392, and displaying theadditional details at 388 is indicated by block 394 in FIG. 5. It can beseen that the display at 388 provides additional information regarding“Company A cross trainers”.

It can also be seen that CRM system 100 displays a button 390 (in theembodiment shown it is in the form of a plus sign) that allows the userto add the suggested products to the “product requirements” for thebusiness opportunity. FIG. 5B shows that the user is touching the button390. This causes CRM system 100 to add the suggested productcorresponding to button 390 to the opportunity record.

FIG. 5C shows a user interface display 396 which is similar to userinterface display 386 shown in FIG. 5B, except that the “Company A crosstrainer bikes” have now been added to the product requirements for thebusiness opportunity record, shown generally at 378. Receiving the touchgesture to add the additional product information to the opportunityrecord is indicated by block 398 in FIG. 5, and having system 100 addthat information to the opportunity record is indicated by block 400 inFIG. 5. Again, it will be appreciated that system 100 can add theinformation by copying all of the information related to the “Company Across trainers” into the opportunity record, or it can create a link inthe opportunity record to the additional information, or both. In anycase, it can now be seen that the business opportunity recordcorresponding to the ACME Company has both performance tires and CompanyA cross trainer bikes as product information which can potentially besold to the ACME Company.

FIG. 6 is a flow diagram illustrating one embodiment of the operation ofthe system shown in FIG. 1 in allowing user 108 to identify decisionmakers for a company corresponding to a business opportunity, and addthem to the business opportunity record in CRM system 100. FIGS. 6A-6Iare illustrative user interface displays. FIGS. 6-6I will now bediscussed in conjunction with one another.

Decision maker selection component 117 first uses user interfacecomponent 112 to generate and display a user interface display thatallows user 108 to add decision makers to the opportunity record. Thisis indicated by block 402 in FIG. 6.

FIG. 6A shows one embodiment of a user interface display 404 that allowsuser 108 to do this. It can be seen that user interface display 404 issimilar to user interface display 276 shown in FIG. 5A and similar itemsare similarly numbered. However, it can be seen that the user has nowtouched the “key decision makers” button 406. This causes user interfacedisplay 404 to display a text box 408 that allows user 108 to enter thenames of key decision makers for the present opportunity, using keyboard308. User 108 then provides a touch input (such as by using virtualkeyboard 308) to provide partial information for the decision makers, byentering text in box 408. This is indicated by block 409 in FIG. 6.

FIG. 6B shows one embodiment of a user interface display 410, which issimilar to user interface display 404 shown in FIG. 6A, and similaritems are similarly numbered. However, in FIG. 6B, it can be seen thatuser 108 has entered partial information “John S.” in text box 408 usingtouch inputs on keyboard 308. User 108 can then optionally touch the“search” button 414. This can cause search component 111 to beginsearching based on the partial information input in text box 408. Itwill also be noted that if system 100 includes a search-as-you-typefunction, then as user 108 is typing information in text box 408, searchcomponent 111 is performing searches, and refining the searches, basedon additional information typed into text box 408. In any case, at somepoint, search component 111 searches internal or external data stores,or both, for additional information. This is indicated by block 416 inFIG. 6, and the searching can be performed in any of a variety ofdifferent ways.

For example, search component 111 can perform the searching based on thespelling or letters input in text box 408. This is indicate by block 418in FIG. 6. Search component 111 can also illustratively search based onconnection graphs 139 in data store 102. For instance, if a givenindividual not only has the first name John and the first letter of hislast name is S, but he also has a strong connection to the uppermanagement in the ACME Company, then this information can be used topreferentially return data corresponding to that individual as apotential decision maker. This is indicated by block 419. Of course,search component 111 can use other information as well in returningsearch results, such as the context of the search (e.g., whether thesearch is for a financial person, a decision maker, a purchasing agent,a sales representative, etc.) as indicated by block 421, or using othersearch criteria as indicated by block 423.

In any case, search component 111 illustratively returns the informationto decision maker selection component 117 which generates a userinterface display (using user interface component 112) identifyingpotential key decision makers based upon the partial information inputin text box 408. Generating and displaying the suggestions for the keydecision makers is indicated by block 418 in FIG. 6, and the display ofthe key decision makers is shown generally at 420 on display 412 of FIG.6B.

It can be seen in FIG. 6B that two key decision makers have beenidentified. Each of the entries under the Key Decision Makers at 420 isillustratively a user actuatable button or link which, when actuated bythe user, causes decision maker selection component 117 to retrieve anddisplay additional information corresponding to the individual personidentified.

FIG. 6C shows an exemplary user interface display 422, that is similarto user interface display 412 shown in FIG. 6B, and similar items aresimilarly numbered. However, FIG. 6C shows that the user has touched thefirst entry under the key decision makers (for John Snowman). Thiscauses decision maker selection component 117 to display the additionalinformation (such as profile information) corresponding to John Snowmanin the additional information section 424. Receiving the touch gestureto display additional details is indicated by block 428 in FIG. 6, anddisplaying the additional details is indicated by block 430. In theembodiment shown in FIG. 6C, the additional information can take anumber of different forms. For example, section 424 is provided with twouser actuatable buttons, including a profile button 432 and aconnections button 434. FIG. 6C shows that the user has actuated theprofile button 432 so that the additional information shown at 424 isprofile information corresponding to John Snowman. Profile informationis indicated by block 436 in FIG. 6.

However, when the user actuates connections button 434, this causesconnection generator 113 in CRM system 100 to display the connectiongraph indicating how user 108 is connected to John Snowman. Theconnection graph is indicated by block 438 in FIG. 6, and one embodimentof this is shown in FIG. 6D. FIG. 6D shows a user interface display 440,which is similar to user interface display 22 shown in FIG. 6C, andsimilar items are similarly numbered. However, FIG. 6D shows that,because the user 108 has actuated the connections button 434, aconnection graph 438 is displayed in section 424 as the more detailedinformation corresponding to John Snowman. The connection graph showshow user 108 is connected to John Snowman. Of course, the additionalinformation 424 can take other forms as well, and this is indicated byblock 442 in FIG. 6.

User interface display 422 also has addition button 426 displayedadjacent the key decision maker entry which allows the user 108 to addthat person to the opportunity record. FIG. 6E also shows user interfacedisplay 448 in which user 108 has touched the addition button 426 to addJohn Snowman to the opportunity record as a key decision maker.Receiving the touch gesture to add the decision maker is indicated byblock 444 in FIG. 6. In response, decision maker selection component 117adds John Snowman to the opportunity record in CRM system 100. This isindicated by block 446 in FIG. 6. It can be seen that user interfacedisplay 448 is similar to user interface display 440 shown in FIG. 6D,except that user interface display 448 now shows that John Snowman hasbeen added as a key decision maker to the opportunity record in text box408.

Of course, the process can be repeated to add additional decision makersas well. For instance, FIG. 6F shows one embodiment of a user interfacedisplay 450. User interface display 450 shows that user 108 has enteredmore partial information in text box 408. Specifically, the user hasentered “Susan S”. This causes search component 111 to conduct anothersearch and return information for decision maker selection component117. In response, component 117 generates a display of a suggested keydecision maker “Susan Snowwoman”. When the user touches that entry,additional information section 424 is updated with additionalinformation (such as profile information or a connection graph)indicating profile information for Susan Snowwoman or showing aconnection graph of how user 108 is connected to Susan Snowwoman. FIG.6F shows that the user has selected the connections button 434 so aconnection graph is shown. FIG. 6G shows a user interface display 452that shows the user has selected the profile button 432 so that profileinformation is shown. FIG. 6G also shows that the user is actuating anaddition button 453 corresponding to the Susan Snowwoman link under thekey decision makers at 420. This adds Susan Snowwoman as a key decisionmaker in the opportunity record and this is shown in the user interfacedisplay 454 in FIG. 6H.

FIG. 6I is an exemplary user interface display 456. User interfacedisplay 456 now shows that, during the call with Phil B., theopportunity record was updated to include not only the productrequirements of the opportunity, but also to identify the key decisionmakers at the ACME Company (the company for which the opportunity recordis being generated).

FIG. 7 is a flow diagram illustrating one embodiment of the operation ofthe system 100 shown in FIG. 1 in configuring a team and assigning teammembers to a business data record. More specifically, FIG. 7 shows oneembodiment of selecting and assigning team members to a businessopportunity data record in CRM system 100. FIGS. 7A-7I are illustrativeuser interface displays. FIGS. 7-7I will now be described in conjunctionwith one another.

In the embodiment shown in FIG. 7, team selector component 116 firstgenerates a user interface display with user input mechanisms that allowuser 108 to select and assign a team to the opportunity record. This isindicated by block 460 in FIG. 7.

The user input mechanisms can allow user 108 to configure the team, suchas by specifying the various positions that are to be filled for theteam. This is indicated by block 462. The user interface display canalso indicate which positions have already been filled as indicated byblock 464, and which positions are empty as indicated by block 466.Further, suggestion component 115 can suggest individuals to fill thevarious empty positions on the team, and this is indicated by block 468.

The user interface display can also illustratively provide search userinput mechanisms that allow user 108 to search the personnel informationin CRM data store 102 to identify various persons that may beappropriate team members. This is indicated by block 468. Of course, theuser interface display can include other items as well, and this isindicated by block 470.

FIG. 7A is one illustrative user interface display 472 that allows theuser to begin the process of selecting and assigning a team to theopportunity record. User interface display 472 illustratively includes auser actuatable research button 474. When button 474 is actuated by theuser, a dropdown menu is displayed, such as menu 476 shown in FIG. 7B.Dropdown menu 476 allows the user to choose one of a number of differentoptions for further adding information to, or configuring, theopportunity represented by user interface display 472. For instance, theuser can assign the opportunity to a company or to a primary contact orother personnel as indicated by button 473. The user can input specificsabout the opportunity or associate contacts to the opportunity asindicated by buttons 475 and 477. All of these operations have beencompleted in the embodiment shown in FIG. 7B. The user can also createan opportunity team by actuating button 478 from dropdown menu 476 ordraft a proposal by actuating button 479. FIG. 7B shows that the user isactuating button 478 to create an opportunity team.

In response to actuating button 478, team selector component 116 usesuser interface component 112 to generate a user interface that allowsuser 108 to select team members and assign them to a team associatedwith the opportunity represented by user interface display 472. FIG. 7Cshows one embodiment of a user interface display 480 that allows user108 to do this. It can be seen that user interface display 480 show inFIG. 7C has a team selector search box (or team selector field) 482 thatallows the user to type in search criteria so that search component 111can search for appropriate possible team members. User interface display480 also has a position bar 484 with a plurality of buttons, one buttoncorresponding to each of a variety of different positions on the team.When the user selects and actuates one of the buttons in position bar484, a suggestion field 486 is populated by suggestion component 115 andteam selector component 116 with suggestions to fill the positioncorresponding to the actuated button. For instance, in the embodimentshown in FIG. 7C, the “executive sponsor” team position button has beenselected and actuated by the user. Therefore, field 486 includes aplurality of different suggestions for filling the “executive sponsor”position. By touching the plus sign adjacent the corresponding name insuggestion field 486, user 108 can assign that individual (or at leastrequest them to be assigned) to the identified position in bar 484.

FIG. 7C also shows that user interface display 480 illustrativelyincludes a team field 488. Team field 488 includes the various positionsthat are to be filled for the team, along with the identity of anindividual who has filled each position, or an indication that theposition has not yet been filled. For instance, user interface display480 shows that the executive sponsor position has been filled by “MikeC.”. An indication that Mike C. has finally been assigned to thisposition is shown at 490. That is, the lock indicates that Mike C. hasbeen finally assigned to (or is locked into) the position. Similarly,field 488 shows that the sales representative position has been filledby Paul W. However, field 488 also shows that a sales assistant positionand a finance consultant position have not yet been filled.

Each of the positions in field 488 illustratively has a correspondinguser actuable input mechanism identified by box 489, 491, 492 and 493.These boxes are, of course, exemplary only. FIG. 7C shows that the useris selecting an open position (the sales assistant position) by touchingthe button or user actuatable input mechanism 492 associated with thatposition. Of course, it will be noted that the user could also entersearch criteria into box 482 in order to obtain suggestions to fill aposition as well. The user selecting either an open position or enteringsearch criteria is indicated by block 494 in the flow diagram of FIG. 7.

Because the user has touched the sales assistant button 492, teamselector component 116 uses user interface component 112 to generate auser interface display with suggestions to fill the empty position.Receiving the touch gesture on the open sales assistant position asindicated by block 496 in FIG. 7 and generating the display withsuggestions to fill the empty position as indicated by block 498.

FIG. 7D is one illustrative user interface display 500 that shows asuggestion field 502 that provides suggestions for the sales assistantposition. It can be seen that, in one embodiment, the suggestion field502 provides two suggestions for the sales assistant position. The firstis Paul W. and the second is Sonja M. Both suggestions have acorresponding user actuatable input mechanism 503 and 505. It can beseen that each of the suggestions also has a percent associatedtherewith. The percent can be calculated by suggestion component 115based on a variety of different criteria. For instance, the percent maybe calculated based on how likely it is that the sales assistant willclose a sale with the company represented by the business opportunity.This may be based on the sales assistant's prior sales history with thatcompany, based on prior sales history within the field, based upon theparticular sales assistant experience, or based on a wide variety ofother criteria. These are listed for the sake of example only. In anycase, Paul W. has an associated percentage of 80% while Sonja M. has anassociated percentage of 67%.

FIG. 7D shows that the user 108 is selecting Paul W. This can be done ina number of different ways. For instance, in the embodiment shown inFIG. 7D, the user simply needs to touch the Paul W. user input mechanism503. However, in another embodiment, the user first selects the Paul W.user input mechanism 503 and then touches the “add” button 504associated with the Paul W. field. In any case, receiving the touchinput adding a suggested member to the team is indicated by block 506 inFIG. 7. In response, team selector component 116 adds the selectedindividual to the team, in the corresponding position (in this case, inthe sales assistant position). This is indicated by block 508 in FIG. 7.

Returning again to block 404 in the flow diagram of FIG. 7, the user cantouch the team selector search box 482 in order to input search criteriato define another team position or to find an individual to fill a teamposition, or to perform other searching. FIG. 7E is a user interfacedisplay 510 which shows that the user has touched the team selectorsearch box 482. In one embodiment, team selector component 116 thuscauses a user interface display, such as display 512 shown in FIG. 7F,to be generated. User interface display 512 is similar to user interfacedisplay 510, and similar items are similarly numbered. However, in theuser interface display 512, it can be seen that a soft keyboard 514 isgenerated to receive user touch inputs to input search criteria in teamselector search box 482. FIG. 7F shows that the user has typed the word“engineer” into team selector field 482 and is touching the “search”button 516. Receiving touch inputs with the search criteria is indicatedby block 518 in FIG. 7.

While FIG. 7F shows that the user has input a position (“engineer”) intosearch box 482, the search criteria could be other criteria a well. Theposition is indicated by block 520 in FIG. 7, but the search criteriacould include availability specifying when the “engineer” is to beavailable (such as where the sales opportunity is on a tight or definiteschedule.) This is indicated by block 522. The search criteria couldalso include a skill set that specifies the skills desired for anindividual to fill the position. This is indicated by block 524. Ofcourse, the search criteria could be other criteria as well, and this isindicated by block 526 in FIG. 7.

Once the user has actuated the search button 516 on keyboard 514,suggestion component 115 uses user interface component 112 to populatethe suggestion field 486 with suggestions of individuals who meet thesearch criteria entered in search box 482. FIG. 7G shows one embodimentof a user interface display 528 that illustrates this. User interfacedisplay 528 shows that suggestion field 486 now has a plurality ofdifferent sections, each associated with a user actuatable button, ofindividuals that can fill the “engineering” position entered in searchbox 482. Generating and displaying the suggestions for a team member isindicated by block 530 in FIG. 7. FIG. 7G also shows that the user isselecting the user actuatable button 531 associated with one of theentries in field 486. In the embodiment shown, user 108 is selectingbutton 531 for “David B.” who is a mechanical engineer.

This causes team selector component 116 to use user interface component112 to generate a user interface display, such as user interface display532 shown in FIG. 7H. User interface display 532 shows that the user hasselected “David B.” and the user interface display, in one embodiment,shows a plurality of different mechanisms by which the individual can becontacted, generally indicated at 534, and also includes an “add” button536 to add the corresponding individual to the team. FIG. 7H shows thatthe user has actuated add button 536. Receiving the touch input adding asuggested team member to the team for the opportunity record isindicated by block 538 in FIG. 7.

As a result of adding David B. to fill the engineering position, teamselector component 116 uses user interface component 112 to generate auser interface display, such as user interface display 540 shown in FIG.7I. User interface display 540 shows that David B. has been added tofill the engineering position, and this is shown generally at 542.

Of course, the above processes described with respect to FIGS. 7-7I canbe repeated to add additional team members to the team for theopportunity. This is indicated by block 544 in FIG. 7.

If the user has finished selecting team members, the user can simplyactuate the “back” button 546 to return to the basic opportunity recordto exit the team selection experience and revert back to the basicopportunity record. This is also shown in FIG. 7I.

FIG. 8 is a flow diagram illustrating one embodiment of the operation ofthe system shown in FIG. 1 in allowing user 108 to manipulate a documentwithin CRM system 100. FIGS. 8A-8O are illustrative user interfacedisplays. FIGS. 8-8O will now be described in conjunction with oneanother.

Management component 119 first uses user interface component 112 togenerate a user interface display that has user input mechanisms thatallow user 108 to manipulate a document corresponding to the opportunityrecord in the CRM system 100. This is indicated by block 550 in FIG. 8.FIG. 8A shows one embodiment of a user interface display 552 that allowsthe user to do this. User interface display 552 is similar to userinterface 228 shown in FIG. 3C, and similar items are similarlynumbered. However, user interface display 552 shows that the user isactuating the “add post” text box 554 under the “what's new” section (orwall).

In response, document management component 119 generates user interfacedisplay 556 shown in FIG. 8B. It can be seen that the user 108 isprovided with a number of user input mechanisms that allow user 108 tomanipulate a post that is made to the “what's new” wall. In oneembodiment, the buttons include an attachment button 558. User interfacedisplay 556 shows that the user is actuating button 558.

In response, document management component 119 generates a userinterface display, such as display 560 shown in FIG. 8C. User interfacedisplay 560 is similar to user interface display 556, except that it nowprovides user input mechanisms (or section) 562 that allow the user toidentify a specific document that is to be attached to the post. In theembodiment shown, the documents include presentation 564, proposal 566,and order 568. The user is also provided a user input mechanism 570 thatallows user 108 to add another file as well. In any case, the documentsidentified in section 562 are illustratively documents that correspondto the sales opportunity record for which user interface display 560 isdisplayed. FIG. 8C shows that the user is touching the user inputmechanism associated with proposal 566. Receiving the touch gestureidentifying and accessing a given document is indicated by block 572 inFIG. 8.

Document management component 119 then retrieves the selected document(the proposal) from data store 102 or from another location and displaysit for user manipulation. In one embodiment, component 119 uses userinterface component 112 to generate one or more user interface displayswith user input mechanisms that receive touch inputs from the user 108,so user 108 can manipulate the selected document. Receiving the touchgestures is indicated by block 574 in FIG. 8. The manipulation steps cantake a wide variety of different forms. For instance, manipulating thedocument can simply mean attaching it to a post as indicated by block576. It can also mean editing the document itself as indicated by block578, or sending a follow-up regarding the document as indicated by block580. In addition, the manipulation can include communicating with othersabout the document (e.g, asking others for assistance in modifying orediting the document or preparing the document, etc.) as indicated byblock 582, or sending the document out for review as indicated by block584. Of course, the manipulation steps could take a wide variety ofother forms as well, and this is indicated by block 586.

Once the user touch gestures are received to manipulate the document,document management component 119 performs the manipulation on thedocument based upon the touch inputs. This is indicated by block 588 inFIG. 8.

FIGS. 8D-8O are exemplary user interface displays that are generated bydocument management component 119 or follow-up component 120, using userinterface component 112. These user interface displays illustrativelyallow user 108 to perform various document manipulation operations.

FIG. 8D shows one illustrative user interface display 590. Userinterface display 590 shows a document section 592 that displays theselected document. Display 590 also includes a wall section 594 thatdisplays a wall corresponding to the document displayed in section 592.Wall section 594 includes an identifying portion 596 that identifies thedocument in section 592. It also identifies the primary contact for thedocument. In addition, in the embodiment shown in FIG. 8D, userinterface 590 includes a recommendation section 598 that recommendsadditional sections to be added to the document shown in section 592.The recommended sections shown at 598 include “company history”,“competitive analysis”, “extended service plan”, and “productcomparison”. In the embodiment shown, each of the recommended sectionshas an associated user actuatable button 601, 603, 605 and 607,respectively.

When the user actuates one of the buttons, the section is automaticallyadded to the document shown at 592. FIG. 8D shows that the user isselecting button 601 the “company history” section for addition to thedocument. This causes document management component 192 to generate adisplay that allows the user to add the selected section to thedocument.

FIG. 8E shows a user interface display 600 that is similar to display590 shown in FIG. 8D, and similar items are similarly numbered. However,user interface display 600 shows that, since the user has selected the“company history” button 601, it is highlighted on the display and anaddition button 602 is added that allows the user to add the section tothe document. FIG. 8E shows that the user 108 is actuating the additionbutton 602 to add the “company history” section to the document shown at592.

FIG. 8E also shows that document management component 119 generates anddisplays a summary section 604 that describes how the probability ofsuccess improves based on the addition of the “company history” sectionto the proposal document. The narrative can be generated using a widevariety of different information sources. For instance, documentmanagement component 119 can track how many proposals are successful indifferent technology areas, and can calculate the percentage based onthat. Of course, the document management component 119 can generate thenarrative in a wide variety of other ways as well, including having ithand written by a human, based on off-line analysis. In any case, FIG.8E shows that the user is selecting the company history section byactuating button 602.

FIG. 8F shows a user interface display 606. User interface display 606is similar to user interface display 600 shown in FIG. 8E, and similaritems are similarly numbered. However, it can be seen in FIG. 8F thatthe document at 592 now includes a second appendix “Appendix B: Thehistory of Contoso” which was automatically added by document managementcomponent 119 once the user added that section to the proposal bytouching the add button 602 (shown in FIG. 8E). FIG. 8F also shows thatthe “company history” section 608 has a check mark next to it,indicating that it has been added to the proposal at 592.

It can also be seen in FIG. 8F that the user has touched the “What'sNew” text box 554. This results in another user interface display. FIG.8G shows a user interface display 610 which is similar to user interfacedisplay 606 shown in FIG. 8F, and similar items are similarly numbered.However, FIG. 8G shows that the dropdown menu containing a plurality ofbuttons (also seen in FIG. 8C) is shown. Among the buttons are theattachment button 558 which allows the user 108 to attach a document, aswell as flag or follow-up button 612. Actuation of button 612 allowsuser 108 to set a follow-up right from the document wall section 594.FIG. 8H shows that the user has actuated the follow-up button 612 andhas also entered text directed at an individual (Ted C.).

FIG. 8I shows another user interface display 611 which results from theuser actuating the follow-up button 612. Follow-up component 120generates the user interface display 611 shown in FIG. 8I which allowsthe user to set a time period for the follow-up. The time periods shownin FIG. 8I are each associated with a user actuatable button. Thebuttons include a today button 614, a tomorrow button 616, a this weekbutton 618 and a next week button 620. The buttons, when actuated,indicate when the follow-up is to be sent to the individual identifiedat 554 in FIG. 8H. FIG. 8I also shows that the user has selected the“today” button 614.

FIG. 8J shows another user interface display 621 in which the user isactuating the “post” button 622. This causes the message typed in textbox 554 to be posted under the “what's new” section on the wall 594.FIG. 8K shows user interface display 623 that illustrates this. It canbe seen that the post that was written by the user and had a follow-upplaced on it is now displayed as the second message under the what's newsection, and the flagged display 650 indicates that a follow-up isrequired by another individual.

FIG. 8K also shows that the recipient of the follow-up has commented onthe section referred to therein. That is, the follow-up asks Ted C. ifhe can look at the methodology section of the proposal. Ted C. has thenresponded (under the what's new section) that he has updated theengineering costs, etc. When that happens, a message indicator 652 isdisplayed adjacent the “methodology” section of the proposal. FIG. 8Kshows that the user is actuating the message indicator 652.

FIG. 8L shows a user interface display 654 that is generated when user108 actuates message indicator 652. It can be seen that an instantmessaging box 656 is displayed. The message from Ted C. is shown in textbox 658. A reply text box 660 is also displayed where the user canreply. In doing so, the user can simply touch box 660 and the virtual orsoft keyboard is displayed so the user can type a message and send itback to Ted C.

FIG. 8M shows another user interface display 662. In user interfacedisplay 662, the user has touched the proposal button 664 and a dropdownmenu 666 is displayed with a plurality of different tasks. The tasksshown include “create proposal”, “tailor specifics”, “send for review”,“present to customer”, and “capture customer feedback”. It can be seenthat check marks 668 show that the first two items in dropdown menu 666have been completed and the user is touching an actuatable button 670 tosend the proposal for review.

FIG. 8N shows a user interface display 672 in which popup menu (or popupdisplay) 674 is displayed allowing user 108 to send the proposal forreview. Popup display 674 shows an example where both interim reviewersand final reviewers can be selected. It can be seen that an interimreviewer has not yet been assigned. However, two final reviewers havebeen assigned. Therefore, when the user touches the send button 676, theproposal is sent to the final reviewers. Once this is complete, the usercan return to the main user interface display for the opportunity datarecord.

FIG. 8O shows one embodiment of a user interface display 680. The userinterface display 680 is similar to user interface display 228 shown inFIG. 3C, and similar items are similarly numbered. However, it can beseen that the “what's new” section has now been updated to reflect anumber of the tasks that have been performed. For instance at 682 thesection shows that a phone call was made to the primary contact, Phil B.At 684 it shows that the opportunity team was created. At 686, thesection illustrates that the proposal was created, and at 688, thesection indicates that the proposal was submitted for review orapproval.

It will be noted that the tasks, operations, and workflows discussedherein are exemplary only. It will also be noted that the user interfacedisplays are exemplary as well. It can be seen, however, that the user108 can perform a variety of different workflows, operations and taskswithin the business data system (e.g., the CRM system 100) using onlytouch gestures or touch inputs. It also allows the user to conduct workfrom a device that has a touch sensitive display. This can enhanceproductivity and reduce the cumbersome and time consuming nature ofusing other types of user input mechanisms.

FIG. 9 is a block diagram of system 100, shown in FIG. 1, except that itis disposed in a cloud computing architecture 700. Cloud computingprovides computation, software, data access, and storage services thatdo not require end-user knowledge of the physical location orconfiguration of the system that delivers the services. In variousembodiments, cloud computing delivers the services over a wide areanetwork, such as the internet, using appropriate protocols. Forinstance, cloud computing providers deliver applications over a widearea network and they can be accessed through a web browser or any othercomputing component. Software or components of system 100 as well as thecorresponding data, can be stored on servers at a remote location. Thecomputing resources in a cloud computing environment can be consolidatedat a remote data center location or they can be dispersed. Cloudcomputing infrastructures can deliver services through shared datacenters, even though they appear as a single point of access for theuser. Thus, the components and functions described herein can beprovided from a service provider at a remote location using a cloudcomputing architecture. Alternatively, they can be provided from aconventional server, or they can be installed on client devicesdirectly, or in other ways.

The description is intended to include both public cloud computing andprivate cloud computing. Cloud computing (both public and private)provides substantially seamless pooling of resources, as well as areduced need to manage and configure underlying hardware infrastructure.

A public cloud is managed by a vendor and typically supports multipleconsumers using the same infrastructure. Also, a public cloud, asopposed to a private cloud, can free up the end users from managing thehardware. A private cloud may be managed by the organization itself andthe infrastructure is typically not shared with other organizations. Theorganization still maintains the hardware to some extent, such asinstallations and repairs, etc.

In the embodiment shown in FIG. 9 some items are similar to those shownin FIG. 1 and they are similarly numbered. FIG. 9 specifically showsthat CRM system 100 (or, of course, another business data system such asan ERP system, LOB application, etc.) is located in cloud 702 (which canbe public, private, or a combination where portions are public whileothers are private). Therefore, user 108 uses a user device 104 toaccess those systems through cloud 702.

FIG. 9 also depicts another embodiment of a cloud architecture. FIG. 9shows that it is also contemplated that some elements of business system100 (or architecture 90) are disposed in cloud 702 while others are not.By way of example, data store 102 can be disposed inside of cloud 702(with CRM system 100) or outside of cloud 702, and accessed throughcloud 702. In another embodiment, communication component 114 is alsooutside of cloud 702. Regardless of where they are located, they can beaccessed directly by device 104, through a network (either a wide areanetwork or a local area network), they can be hosted at a remote site bya service, or they can be provided as a service through a cloud oraccessed by a connection service that resides in the cloud. All of thesearchitectures are contemplated herein.

It will also be noted that system 100, or portions of it, can bedisposed on a wide variety of different devices. Some of those devicesinclude servers, desktop computers, laptop computers, tablet computers,or other mobile devices, such as palm top computers, cell phones, smartphones, multimedia players, personal digital assistants, etc.

FIG. 10 is a simplified block diagram of one illustrative embodiment ofa handheld or mobile computing device that can be used as a user's orclient's hand held device 16 (e.g., device 104), in which the presentsystem (or parts of it) can be deployed. FIGS. 10-14 are examples ofhandheld or mobile devices.

FIG. 10 provides a general block diagram of the components of a clientdevice 16 that can run components of system 100 or that interacts withsystem 100, or both. In the device 16, a communications link 13 isprovided that allows the handheld device to communicate with othercomputing devices and under some embodiments provides a channel forreceiving information automatically, such as by scanning. Examples ofcommunications link 13 include an infrared port, a serial/USB port, acable network port such as an Ethernet port, and a wireless network portallowing communication though one or more communication protocolsincluding General Packet Radio Service (GPRS), LTE, HSPA, HSPA+ andother 3G and 4G radio protocols, 1Xrtt, and Short Message Service, whichare wireless services used to provide cellular access to a network, aswell as 802.11 and 802.11b (Wi-Fi) protocols, and Bluetooth protocol,which provide local wireless connections to networks.

Under other embodiments, applications or systems (like system 100) arereceived on a removable Secure Digital (SD) card that is connected to aSD card interface 15. SD card interface 15 and communication links 13communicate with a processor 17 (which can also embody processor 146from FIG. 1) along a bus 19 that is also connected to memory 21 andinput/output (I/O) components 23, as well as clock 25 and locationsystem 27.

I/O components 23, in one embodiment, are provided to facilitate inputand output operations. I/O components 23 for various embodiments of thedevice 16 can include input components such as buttons, touch sensors,multi-touch sensors, optical or video sensors, voice sensors, touchscreens, proximity sensors, microphones, tilt sensors, and gravityswitches and output components such as a display device, a speaker, andor a printer port. Other I/O components 23 can be used as well.

Clock 25 illustratively comprises a real time clock component thatoutputs a time and date. It can also, illustratively, provide timingfunctions for processor 17.

Location system 27 illustratively includes a component that outputs acurrent geographical location of device 16. This can include, forinstance, a global positioning system (GPS) receiver, a LORAN system, adead reckoning system, a cellular triangulation system, or otherpositioning system. It can also include, for example, mapping softwareor navigation software that generates desired maps, navigation routesand other geographic functions.

Memory 21 stores operating system 29, network settings 31, applications33, application configuration settings 35, data store 37, communicationdrivers 39, and communication configuration settings 41. Memory 21 caninclude all types of tangible volatile and non-volatilecomputer-readable memory devices. It can also include computer storagemedia (described below). Memory 21 stores computer readable instructionsthat, when executed by processor 17, cause the processor to performcomputer-implemented steps or functions according to the instructions.System 100 or the items in data store 102, for example, can reside inmemory 21. Similarly, device 16 can have a client business system 24(e.g., client CRM system 144) which can run various businessapplications or embody parts or all of business system 100. Processor 17can be activated by other components to facilitate their functionalityas well.

Examples of the network settings 31 include things such as proxyinformation, Internet connection information, and mappings. Applicationconfiguration settings 35 include settings that tailor the applicationfor a specific enterprise or user. Communication configuration settings41 provide parameters for communicating with other computers and includeitems such as GPRS parameters, SMS parameters, connection user names andpasswords.

Applications 33 can be applications that have previously been stored onthe device 16 or applications that are installed during use, althoughthese can be part of operating system 29, or hosted external to device16, as well.

FIG. 11 shows one embodiment in which device 16 is a tablet computer 750(also shown in FIGS. having illustrative displays discussed above).Screen 752 can be a touch screen (so touch gestures from a user's fingercan be used to interact with the application) or a pen-enabled interfacethat receives inputs from a pen or stylus. It can also use an on-screenvirtual keyboard. Of course, it might also be attached to a keyboard orother user input device through a suitable attachment mechanism, such asa wireless link or USB port, for instance. Computer 750 can alsoillustratively receive voice inputs as well.

FIGS. 12, 13 and 14 provide additional examples of devices 16 that canbe used, although others can be used as well. In FIG. 12, a mobile phone45 (or feature phone) is provided as the device 16. Phone 45 includes aset of keypads 47 for dialing phone numbers, a display 49 capable ofdisplaying images including application images, icons, web pages,photographs, and video, and control buttons 51 for selecting items shownon the display. The phone includes an antenna 53 for receiving cellularphone signals such as General Packet Radio Service (GPRS) and 1Xrtt, andShort Message Service (SMS) signals. In some embodiments, phone 45 alsoincludes a Secure Digital (SD) card slot 55 that accepts a SD card 57.

The mobile device of FIG. 13 is a personal digital assistant (PDA) 59 ora multimedia player or a tablet computing device, etc. (hereinafterreferred to as PDA 59). PDA 59 includes an inductive screen 61 thatsenses the position of a stylus 63 (or other pointers, such as a user'sfinger) when the stylus is positioned over the screen. This allows theuser to select, highlight, and move items on the screen as well as drawand write. PDA 59 also includes a number of user input keys or buttons(such as button 65) which allow the user to scroll through menu optionsor other display options which are displayed on display 61, and allowthe user to change applications or select user input functions, withoutcontacting display 61. Although not shown, PDA 59 can include aninternal antenna and an infrared transmitter/receiver that allow forwireless communication with other computers as well as connection portsthat allow for hardware connections to other computing devices. Suchhardware connections are typically made through a cradle that connectsto the other computer through a serial or USB port. As such, theseconnections are non-network connections. In one embodiment, mobiledevice 59 also includes a SD card slot 67 that accepts a SD card 69.

FIG. 14 is similar to FIG. 13 except that the phone is a smart phone 71.Smart phone 71 has a touch sensitive display 73 that displays icons ortiles or other user input mechanisms 75. Mechanisms 75 can be used by auser to access a business data system (like CRM system 100) runapplications, make calls, perform data transfer operations, etc. Ingeneral, smart phone 71 is built on a mobile operating system and offersmore advanced computing capability and connectivity than a featurephone.

Note that other forms of the devices 16 are possible.

FIG. 15 is one embodiment of a computing environment in which system 100(for example) can be deployed. With reference to FIG. 15, an exemplarysystem for implementing some embodiments includes a general-purposecomputing device in the form of a computer 810. Components of computer810 may include, but are not limited to, a processing unit 820 (whichcan comprise processor 110 or 144), a system memory 830, and a systembus 821 that couples various system components including the systemmemory to the processing unit 820. The system bus 821 may be any ofseveral types of bus structures including a memory bus or memorycontroller, a peripheral bus, and a local bus using any of a variety ofbus architectures. By way of example, and not limitation, sucharchitectures include Industry Standard Architecture (ISA) bus, MicroChannel Architecture (MCA) bus, Enhanced ISA (EISA) bus, VideoElectronics Standards Association (VESA) local bus, and PeripheralComponent Interconnect (PCI) bus also known as Mezzanine bus. Memory andprograms described with respect to FIG. 1 can be deployed incorresponding portions of FIG. 15.

Computer 810 typically includes a variety of computer readable media.Computer readable media can be any available media that can be accessedby computer 810 and includes both volatile and nonvolatile media,removable and non-removable media. By way of example, and notlimitation, computer readable media may comprise computer storage mediaand communication media. Computer storage media is different from, anddoes not include, a modulated data signal or carrier wave. It includeshardware storage media including both volatile and nonvolatile,removable and non-removable media implemented in any method ortechnology for storage of information such as computer readableinstructions, data structures, program modules or other data. Computerstorage media includes, but is not limited to, RAM, ROM, EEPROM, flashmemory or other memory technology, CD-ROM, digital versatile disks (DVD)or other optical disk storage, magnetic cassettes, magnetic tape,magnetic disk storage or other magnetic storage devices, or any othermedium which can be used to store the desired information and which canbe accessed by computer 810. Communication media typically embodiescomputer readable instructions, data structures, program modules orother data in a transport mechanism and includes any informationdelivery media. The term “modulated data signal” means a signal that hasone or more of its characteristics set or changed in such a manner as toencode information in the signal. By way of example, and not limitation,communication media includes wired media such as a wired network ordirect-wired connection, and wireless media such as acoustic, RF,infrared and other wireless media. Combinations of any of the aboveshould also be included within the scope of computer readable media.

The system memory 830 includes computer storage media in the form ofvolatile and/or nonvolatile memory such as read only memory (ROM) 831and random access memory (RAM) 832. A basic input/output system 833(BIOS), containing the basic routines that help to transfer informationbetween elements within computer 810, such as during start-up, istypically stored in ROM 831. RAM 832 typically contains data and/orprogram modules that are immediately accessible to and/or presentlybeing operated on by processing unit 820. By way of example, and notlimitation, FIG. 15 illustrates operating system 834, applicationprograms 835, other program modules 836, and program data 837.

The computer 810 may also include other removable/non-removablevolatile/nonvolatile computer storage media. By way of example only,FIG. 15 illustrates a hard disk drive 841 that reads from or writes tonon-removable, nonvolatile magnetic media, a magnetic disk drive 851that reads from or writes to a removable, nonvolatile magnetic disk 852,and an optical disk drive 855 that reads from or writes to a removable,nonvolatile optical disk 856 such as a CD ROM or other optical media.Other removable/non-removable, volatile/nonvolatile computer storagemedia that can be used in the exemplary operating environment include,but are not limited to, magnetic tape cassettes, flash memory cards,digital versatile disks, digital video tape, solid state RAM, solidstate ROM, and the like. The hard disk drive 841 is typically connectedto the system bus 821 through a non-removable memory interface such asinterface 840, and magnetic disk drive 851 and optical disk drive 855are typically connected to the system bus 821 by a removable memoryinterface, such as interface 850.

The drives and their associated computer storage media discussed aboveand illustrated in FIG. 15, provide storage of computer readableinstructions, data structures, program modules and other data for thecomputer 810. In FIG. 15, for example, hard disk drive 841 isillustrated as storing operating system 844, application programs 845,other program modules 846, and program data 847. Note that thesecomponents can either be the same as or different from operating system834, application programs 835, other program modules 836, and programdata 837. Operating system 844, application programs 845, other programmodules 846, and program data 847 are given different numbers here toillustrate that, at a minimum, they are different copies.

A user may enter commands and information into the computer 810 throughinput devices such as a keyboard 862, a microphone 863, and a pointingdevice 861, such as a mouse, trackball or touch pad. Other input devices(not shown) may include a joystick, game pad, satellite dish, scanner,or the like. These and other input devices are often connected to theprocessing unit 820 through a user input interface 860 that is coupledto the system bus, but may be connected by other interface and busstructures, such as a parallel port, game port or a universal serial bus(USB). A visual display 891 or other type of display device is alsoconnected to the system bus 821 via an interface, such as a videointerface 890. In addition to the monitor, computers may also includeother peripheral output devices such as speakers 897 and printer 896,which may be connected through an output peripheral interface 895.

The computer 810 is operated in a networked environment using logicalconnections to one or more remote computers, such as a remote computer880. The remote computer 880 may be a personal computer, a hand-helddevice, a server, a router, a network PC, a peer device or other commonnetwork node, and typically includes many or all of the elementsdescribed above relative to the computer 810. The logical connectionsdepicted in FIG. 15 include a local area network (LAN) 871 and a widearea network (WAN) 873, but may also include other networks. Suchnetworking environments are commonplace in offices, enterprise-widecomputer networks, intranets and the Internet.

When used in a LAN networking environment, the computer 810 is connectedto the LAN 871 through a network interface or adapter 870. When used ina WAN networking environment, the computer 810 typically includes amodem 872 or other means for establishing communications over the WAN873, such as the Internet. The modem 872, which may be internal orexternal, may be connected to the system bus 821 via the user inputinterface 860, or other appropriate mechanism. In a networkedenvironment, program modules depicted relative to the computer 810, orportions thereof, may be stored in the remote memory storage device. Byway of example, and not limitation, FIG. 15 illustrates remoteapplication programs 885 as residing on remote computer 880. It will beappreciated that the network connections shown are exemplary and othermeans of establishing a communications link between the computers may beused.

It should also be noted that features from different embodiments can becombined. That is, one or more features from one embodiment can becombined with one or more features of other embodiments. This iscontemplated herein.

Although the subject matter has been described in language specific tostructural features and/or methodological acts, it is to be understoodthat the subject matter defined in the appended claims is notnecessarily limited to the specific features or acts described above.Rather, the specific features and acts described above are disclosed asexample forms of implementing the claims.

What is claimed is:
 1. A computing device, comprising: a touch sensitivedisplay screen; a user interface component displaying a user interfacedisplay from a business data system on the touch sensitive displayscreen and receiving a user touch gesture through the user interfacedisplay; a business data component manipulating the business data systemto perform an operation in the business data system based on the touchgesture; and a computer processor, being a functional part of thecomputing device and activated by the user interface component and thebusiness data component to facilitate displaying, receiving the usertouch gesture, and performing the operation.
 2. The computing device ofclaim 1 wherein the touch gesture comprises a search input touch gestureand wherein the business data component comprises a search componentthat searches for information based on the search input touch gesture.3. The computing device of claim 2 wherein the search component searchesone or more data stores external to the business data system based onthe search input touch gesture and displays search results along with auser input mechanism corresponding to each result.
 4. The computingdevice of claim 3 wherein the business data component receives a userselection touch gesture actuating a given user input mechanismcorresponding to a given search result.
 5. The computing device of claim4 wherein the business data component adds a link, in a business datarecord, to the given search result based on receiving the user selectiontouch gesture, the link being actuatable to navigate to the given searchresult, with a user actuation touch gesture.
 6. The computing device ofclaim 1 wherein the user touch gesture comprises a decision maker touchgesture and wherein the business data component comprises: a decisionmaker selection component that identifies a decision maker in anorganization external to the business data system based on the decisionmaker touch gesture.
 7. The computing device of claim 6 wherein thedecision maker selection component includes a search component thatreceives a decision maker search user touch gesture and searches forpossible decision makers based on the decision maker search user touchgesture, and wherein the decision maker selection component displays thepossible decision makers along with a user input mechanism correspondingto each possible decision maker.
 8. The computing device of claim 7wherein the decision maker selection component receives a decision makerselection touch gesture actuating a given user input mechanismcorresponding to a given possible decision maker.
 9. The computingdevice of claim 8 wherein the decision maker selection component addsthe given possible decision maker to the business data record based onthe decision maker selection touch gesture.
 10. The computing device ofclaim 8 wherein the decision maker selection component displays profileinformation for the given possible decision maker based on the decisionmaker selection touch gesture.
 11. The computing device of claim 8wherein the decision maker selection component displays a connectiongraph indicating a connection between the user and the given possibledecision maker based on the decision maker selection touch gesture. 12.A computer-implemented method of manipulating a business data system,comprising: displaying a user interface display showing businessinformation from the business data system; receiving a touch gesture onthe user interface display, to perform a given task, operation orworkflow in the business data system; and performing the given task,operation or workflow in the business data system based on the receivedtouch gesture.
 13. The computer-implemented method of claim 12 whereinreceiving the user touch gesture comprises receiving a partialinformation touch gesture partially identifying an item of interest, andfurther comprising: displaying suggestions identifying suggested itemsof interest based on the partial information touch gesture, anddisplaying a touch actuatable input mechanism corresponding to eachsuggested item of interest.
 14. The computer-implemented method of claim12 wherein receiving the user touch gesture comprises receiving a followup touch gesture identifying an item to receive a follow-up message,received on a display of a wall corresponding to a business data record,and further comprising: displaying the follow-up message on a displayindicative of the business data record based on the follow-up touchgesture.
 15. The computer-implemented method of claim 12 whereinreceiving the user touch gesture comprises receiving a documentmanagement touch gesture identifying a document, received on a displayof a wall corresponding to a business data record, and furthercomprising: displaying the identified document and performing a documentmanagement step on the identified document based on the documentmanagement touch gesture.
 16. A business data system, comprising: a userinterface component; a business data component generating a userinterface display, using the user interface component, showing abusiness data record with a user input mechanism used to perform a task,operation or workflow on the business data record, receiving a touchgesture through the user input mechanism to perform the task, operationor workflow, and performing the task, operation or workflow on thebusiness data record in the business data system based on the touchgesture; and a computer processor being a functional part of thebusiness data system and activated by the user interface component andthe business data component to facilitate generating the user interfacedisplay, receiving the touch gesture and performing the task, operationor workflow.
 17. The business data system of claim 16 wherein the touchgesture comprises a team selection touch gesture and wherein thebusiness data component comprises: a team selection component thatidentifies and assigns team members to a team corresponding to abusiness data record in the business data system based on the teamselection touch gesture.
 18. The business data system of claim 17wherein the team selection component includes a search component thatreceives a team search user touch gesture and searches for possible teammembers based on the team search user touch gesture, and wherein theteam selection component displays the possible team members along with auser input mechanism corresponding to each possible team member.
 19. Thebusiness data system of claim 18 wherein the team selection componentreceives a team selection touch gesture actuating a given user inputmechanism corresponding to a given possible team member.
 20. Thebusiness data system of claim 19 wherein the team selection componentadds the given possible team member to the team corresponding to thebusiness data record based on the team selection touch gesture.